A Pattern Architecture: Using patterns to define an overall systems architecture

The notion of patterns has been used in many different disciplines, and the software industry is no exception. There are many books written, academic research done and practical examples available of where patterns have assisted in constructing better software solutions. Patterns have been defined in the areas of software design, architectural design, processes, and there are even cognitive patterns to deal with the softer side of software production. But, with the many variations available today, where do you start? This paper presents an architecture that will assist with the use of patterns. Patterns are used as a means to capitalize on previous innovations and learnings. Once patterns are documented and articulated, the implementor gets the benefits by using a structured approach to implement and by using the principles in many domains. The complexities that surround innovations are normally difficult to articulate in traditional means. A learning model is used to assist in the process of pattern identification. Another model, the Y-Model, is used to deal with understanding complexity and abstractiveness in systems. The pattern architecture presented does not regurgitate patterns available already, but focuses on some of the findings in delivering complex, re-usable business components. This means that a number of new patterns, not publicly documented before, are introduced.